Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release-22.2: workload/mixed-version/schemachanger: re-enable mixed version workload #88536

Merged
merged 4 commits into from
Oct 11, 2022

Conversation

fqazi
Copy link
Collaborator

@fqazi fqazi commented Sep 23, 2022

Re-enables the mixed version workload for 22.2

Backport:

Please see individual PRs for details.

Release note: None
Release justification: low-risk changes to re-enable the mixed version testing workload

/cc @cockroachdb/release

@fqazi fqazi requested review from ajwerner and a team September 23, 2022 03:16
@blathers-crl
Copy link

blathers-crl bot commented Sep 23, 2022

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@ajwerner
Copy link
Contributor

There's something weird in these build failures

@fqazi fqazi force-pushed the backport22.2-87142-88475 branch 2 times, most recently from d546817 to 7975247 Compare October 5, 2022 18:11
Copy link
Contributor

@ajwerner ajwerner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained

…ployed

Previously, the schemachanger mixed version workload did not
deploy the libGEOS libraries causing operations to fail. To address,
this patch will update the frontend to upload these binaries.

Release justification: no real risk improves test coverage
Release note: None
… state

Previously, the schema changer workload in a mixed version state
attempted to use trigram indexes against 22.1, which is unsupported.
This patch adds code to detect a mixed version state and expects
the appropriate error when this occurs.

Release justification: no risk improves test coverage
Release note: None
Previously, if we ran in a mixed version state with the schema changer
workload we could run into an optimizer bug (cockroachdb#80820). To address this,
this patch in a mixed version workload disables the insert portion of
the workload.

Release justification: improves test coverage by enabling the mixed
version test
Release note: None
Fixes: cockroachdb#87768

Previously, we were generating statements with invisible indexes in mixed
version environments, which could lead to statements generated not
supported on older versions. To address this, this patch will prevent
the generation of create table/ create index statements with invisible
indexes.

Release note: None
@fqazi
Copy link
Collaborator Author

fqazi commented Oct 11, 2022

@ajwerner TFTR!

@fqazi fqazi merged commit 98a5776 into cockroachdb:release-22.2 Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants